Skip to main content

Minimum QA testing requirements in Hackney’s Software Development Lifecycle

Context​

This document aims at outlining what are the minimum testing and quality assurance processes that should be done for each project as part of the Software Development Lifecycle.

Each product will be asked to demonstrate sufficient testing performed as per the minimum testing activities described in this document.

HackIT Testing Standards

APIs and Backend services​

Process diagram: Click image to open in a new tab.

All APIs and Backend services must be built following the test driven development approach, as described in our API Playbook.

Tests written by: Software engineers Tests executed by: Software engineers (as part of local testing) and CI/CD pipeline, as part of Continuous Integration

Code testing

Other automated testing

Frontend services​

Process diagram: Click image to open in a new tab.

All Frontend services must have corresponding unit tests implemented as part of a Test Driven Development approach.

Tests written by: Software engineers Tests executed by: Software engineers (as part of local testing) and CI/CD pipeline, as part of Continuous Integration

Code testing

  • Unit testing

Other automated tests

Product testing​

Process diagram: Click image to open in a new tab.

All products must implement E2E testing, using tools such as Cypress, to validate that features are correctly implemented and the frontend and backend are successfully integrated. This step is crucial for the continuous delivery phase.

Tests written by: QA engineers Tests executed by: QA engineers (as part of local testing) and CI/CD pipeline, as part of Continuous Integration